Purpose

https://folio-org.atlassian.net/browse/UISACQCOMP-194

Central ordering in the receiving application implies the possibility of action within two tenants (central and active - system) without switching the active affiliation. To implement this feature, many components must be updated to support sending requests to the specified tenant.

Approach

Most components that load data over the network use the system tenant ID (from the stripes object), so data is always loaded from the active affiliation. It is necessary to update components, hooks, and utilities used in applications where central ordering is required to allow explicit specification of the tenant (tenantId) to which requests should be directed.

Also, to create conditions for reusing hooks and unifying the approach to data loading, components using mutators and stripesConnect are refactored to use react-query hooks.

Screenshot

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

• I've added appropriate record to the CHANGELOG.md
• Does this PR meet or exceed the expected quality standards?
  • Code coverage on new code is 80% or greater
  • Duplications on new code is 3% or less
  • There are no major code smells or security issues
• Does this introduce breaking changes?
  • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
  • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

• What other modules will these changes impact?
• Do JIRAs exist to update the impacted modules?
  • If not, please create them
  • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
  • Do they have all they appropriate links to blocked/related issues?
• Are the JIRAs under active development?
  • If not, contact the project's PO and make sure they're aware of the urgency.
• Do PRs exist for these changes?
  • If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.